home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950929-19951130
/
000241_news@columbia.edu_Mon Oct 30 14:15:16 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
3KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA07272
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 30 Oct 1995 09:17:57 -0500
Received: by apakabar.cc.columbia.edu id AA00337
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 30 Oct 1995 09:15:55 -0500
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Problems with C-Kermit & the modem device
Date: 30 Oct 1995 14:15:16 GMT
Organization: Columbia University
Lines: 42
Distribution: na
Message-Id: <472mlk$6l@apakabar.cc.columbia.edu>
References: <46ok86$f16@maroon.tc.umn.edu>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <46ok86$f16@maroon.tc.umn.edu>,
Sothamith Chau <chau0004@maroon.tc.umn.edu> wrote:
: I am having a problem getting C-Kermit to interact properly on a Sun 1000
: with a telebit modem. C-Kermit functions properly, but after HANGUP and
: leaving the program, users attempting to dial into the machine will
: receieve a connection to the modem, but will never get the login prompt.
:
: We have isolated Kermit as the program affecting a change in the config of
: the modem and port. I can reset the modem/port to allow logins again by
: using 'tip cuab' and sending "ATL7\n", then subsequently issuing
: 'sacadm -x -p zsmon' as superuser. However, I would prefer to address the
: reason why Kermit is changing this configuration, and how, via either some
: commands that I am overlooking, or via a code modification, I can change
: this.
:
This is an open problem. I don't think it's Kermit's "fault". There has
been no end of trouble with ports on Solaris, particularly those that are
set up for bidirectional use, when the same code (more or less) works on
hundreds of other UNIX versions.
According to one informant, there is a bug in Solaris 2.3 that causes this;
bug ID 1191317, and a corresponding patch 101720-02, but there is no
corresponding patch for Solaris 2.4. It's not clear to me whether Sun
acknowledges a bug in Solaris 2.4.
Many people point out that the problem does not happen with TIP, CU, etc.
But that, I believe, is because these are Sun products, which are either
engineered to work around the problem, or are coded to use some API that
we don't know about. Another informant supplies this hint (regarding
TIP): "it opens the port, does an ioctl setflags with XCLUDE and
HUPCL...". Evidently XCLUDE is not documented anywhere, except in the
header file <sys/termios.h> that defines it:
#define XCLUDE 0100000 /* *V7* Exclusive use coming from XENIX */
That's all I know. Further info would be appreciated, especially from
anybody who has a Solaris 2.3 or 2.4 system and a bidirectional port who
can try adding this flag and seeing what difference it makes. In the
meantime, it seems the safest course is (as always) to avoid bidirectional
port setups in Solaris (and most other UNIX variants) whenever possible.
- Frank